Skip to content

Feature: add specify status command#1837

Open
KhawarHabibKhan wants to merge 10 commits intogithub:mainfrom
KhawarHabibKhan:add-status-command
Open

Feature: add specify status command#1837
KhawarHabibKhan wants to merge 10 commits intogithub:mainfrom
KhawarHabibKhan:add-status-command

Conversation

@KhawarHabibKhan
Copy link
Contributor

@KhawarHabibKhan KhawarHabibKhan commented Mar 13, 2026

Summary

  • Adds the spec-kit-status extension to the community catalog
  • Shows current SDD workflow progress: active feature, artifact status, task completion percentage, workflow phase, and extensions
    summary
  • Extension repo: https://github.com/KhawarHabibKhan/spec-kit-status

Changes

  • Added status entry to extensions/catalog.community.json
  • Added Project Status row to extensions/README.md table

Motivation

There is currently no way to see the overall state of a spec-kit project from the CLI. Users must manually check git branches, the file system, and run separate extension commands. This fills that gap — similar to how git status provides a project snapshot.

Note

This was initially submitted as a core CLI command (specify status). Based on reviewer feedback, it has been rebuilt as a standalone extension.

@mnriem
Copy link
Collaborator

mnriem commented Mar 13, 2026

Please deliver this as an extension or does the Project Health extension already fit the bill? See https://github.com/github/spec-kit/tree/main/extensions#available-community-extensions

@mnriem
Copy link
Collaborator

mnriem commented Mar 13, 2026

As in can you add it to it?

@KhawarHabibKhan
Copy link
Contributor Author

Thanks for the feedback! The doctor extension focuses on project health validation (is the setup correct?), while this is about workflow progress tracking, showing current feature, SDD artifact status, task completion percentage, and which workflow phase you're in. They serve different purposes.

I'll revert the core CLI changes and rebuild it as a standalone extension following the same pattern as spec-kit-doctor.

@KhawarHabibKhan KhawarHabibKhan requested a review from mnriem as a code owner March 16, 2026 12:03
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the spec-kit-status community extension so users can view an SDD workflow/project snapshot (active feature, artifact/task progress, phase, installed extensions) via a dedicated status extension.

Changes:

  • Added a new status entry to extensions/catalog.community.json pointing to the v1.0.0 release archive and metadata.
  • Added a “Project Status” row to the community extensions table in extensions/README.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
extensions/catalog.community.json Registers the new status extension in the community catalog.
extensions/README.md Documents the new community extension in the catalog table.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback

KhawarHabibKhan and others added 2 commits March 16, 2026 19:08
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copy link
Contributor Author

@KhawarHabibKhan KhawarHabibKhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved the issues. Please Review.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the community extension spec-kit-status to the Spec Kit community catalog and surfaces it in the extensions README so users can discover a “project status” snapshot via the extension system (rather than a core specify status command).

Changes:

  • Added a new status extension entry to extensions/catalog.community.json (and updated the catalog timestamp).
  • Added a “Project Status” row to the community extensions table in extensions/README.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
extensions/catalog.community.json Adds the status extension metadata entry and updates catalog updated_at.
extensions/README.md Adds “Project Status” to the community extensions list for discoverability.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +518 to 549
"status": {
"name": "Project Status",
"id": "status",
"description": "Show current SDD workflow progress — active feature, artifact status, task completion, workflow phase, and extensions summary.",
"author": "KhawarHabibKhan",
"version": "1.0.0",
"download_url": "https://github.com/KhawarHabibKhan/spec-kit-status/archive/refs/tags/v1.0.0.zip",
"repository": "https://github.com/KhawarHabibKhan/spec-kit-status",
"homepage": "https://github.com/KhawarHabibKhan/spec-kit-status",
"documentation": "https://github.com/KhawarHabibKhan/spec-kit-status/blob/main/README.md",
"changelog": "https://github.com/KhawarHabibKhan/spec-kit-status/blob/main/CHANGELOG.md",
"license": "MIT",
"requires": {
"speckit_version": ">=0.1.0"
},
"provides": {
"commands": 1,
"hooks": 0
},
"tags": [
"status",
"workflow",
"progress",
"feature-tracking",
"task-progress"
],
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-03-16T00:00:00Z",
"updated_at": "2026-03-16T00:00:00Z"
}
@mnriem mnriem self-requested a review March 16, 2026 14:14
Copy link
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there. Please address Copilot feedback and it can be merged :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants